home *** CD-ROM | disk | FTP | other *** search
- • To begin the conflict test, you must restart the computer.
-
- • Click on any files that must be on.
- • The next step is to see if the problem is actually being caused by a startup file.
-
- Click OK and determine if the problem still exists. Then restart your computer.
-
- • Because the problem was gone, there must be a startup file conflict.
- • Conflict Catcher will now activate the files your intuition said contained the problem.
-
- Click OK, determine if the problem exists and restart.
-
- • Because the problem was gone, there must be a startup file conflict.
- • Conflict Catcher will now activate half of the suspect startup files.
-
- Click OK, determine if the problem exists and restart.
-
- • Because the problem was gone, the suspects that were active have been ruled out.
- • Conflict Catcher will now activate half of the remaining suspects.
-
- Click OK, determine if the problem exists and restart.
-
- • Because the problem existed, the suspects that were inactive have been ruled out.
- • Conflict Catcher will now activate half of the remaining suspects.
-
- Click OK, determine if the problem exists and restart.
-
- • The next step is to see if the entire problem has been found.
- • Conflict Catcher will now activate the files found to be part of the problem.
-
- Click OK, determine if the problem exists and restart.
-
- • Because the problem hasn't yet existed during the test, we must verify that it exists.
- • Conflict Catcher will now activate the remaining suspect.
-
- Click OK, determine if the problem exists and restart.
-
- • The entire problem has been identified.
- • Conflict Catcher will now try reordering startup files to see if the problem goes away.
-
- Click OK, determine if the problem exists, and restart.
-
-
